Skip to content

feat: vIP Endpoint Filtering & KUBECONFIG Support#12

Merged
Handfish merged 1 commit intomainfrom
0.1.4
Jan 17, 2026
Merged

feat: vIP Endpoint Filtering & KUBECONFIG Support#12
Handfish merged 1 commit intomainfrom
0.1.4

Conversation

@Handfish
Copy link
Copy Markdown
Owner

When a talosconfig uses a virtual IP or load balancer hostname (e.g., cluster.example.com) as the endpoint, and that same hostname appears in the nodes list, the Talos API would return empty results. This happened because the vIP/hostname was being passed in the gRPC node targeting header, but the Talos API only recognizes actual node IPs.

Modified TalosClient in crates/talos-rs/src/client.rs to:

  • Store the original endpoints when creating the client
  • Filter out any endpoint hostnames from the nodes list before sending requests
  • Also filter out localhost addresses (127.0.0.1, localhost) which are never valid node targets

Also now respecting the KUBECONFIG environment variable.

chore: run fmt

chore: bump version and lint
@Handfish Handfish merged commit 04470d0 into main Jan 17, 2026
12 checks passed
@Handfish Handfish deleted the 0.1.4 branch January 17, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant